home *** CD-ROM | disk | FTP | other *** search
- *************************************************************************
- * CALLBLOC.PPE *
- * A PCBoard 15 Sysop Utility PPE *
- * version: 2.6 date: 5/21/1994 *
- * (c) Copyright 1993 A. Segura/Fax~An~Ad Marketing, Inc. *
- *************************************************************************
-
- THE First!! THE Original!! Caller-ID Call Blocker
-
-
- Purpose: To improve your BBS SECURITY by performing a Caller-ID
- (CID) phone number check before the user gains full access
- to the BBS. The CID check is performed against a file
- of known bad caller's phone numbers previously saved by
- the SysOp or automatically saved by VULGARID.PPE
- (version 2.x). In other words, an online automatic call
- blocker routine. Now supports Deluxe CID Name logging.
-
-
- Features: 1. Extremely user (Sysop) configurable!
- 2. Can be installed in several locations!
- 3. Performs error and self-integrity checks!
- 4. Sends messages to designated Sysop for both Abusive
- and Private detected callers!
- 5. Optionally writes all calls to log!
- 6. Allows security, language and graphics extension
- text display files!
- 7. All display and message files are user editable!
- 8. Can be placed in ANY directory!
- 9. Built-in Defaults option for increased speed!
- 10. Allows user-defined modem type!
-
- And on, and on, and on........
-
- NOTE: Due to the extensive revision of CALLBLOC
- version 2.x, VULGARID version 1.x will not
- function properly with CALLBLOC 2.x. IF you
- are using or desire to use VULGARID, then
- you must install VULGARID version 2.x.
-
-
- Additional
- Requirements: 1. PCBoard version 15.x.
- 2. Caller-ID capable modem (such as Supra or ZyXEL).
- 3. Caller-ID service from local phone company.
-
- NOTE: You do not need any other external
- Caller-ID box/device!!
-
-
- Zip File
- Contents: 1. BADCALL a sample abusive caller text display file.
- 2. BADCALL.NUM a sample blocked phone number file.
- 3. BAD-MSG a sample bad call sysop message text file
- 4. BLOCKED a sample Private caller display file.
- 5. CALLBLOC.CFG the configuration file for CALLBLOC.PPE
- 6. CALLBLOC.DOC this file.
- 7. CALLBLOC.LOG a sample call log
- 8. CALLBLOC.PPE the subject PPE file.
- 9. FILE_ID.DIZ a brief BBS text description of this item.
- 10. PRIV-MSG a sample private call sysop message text file
- 11. RECALL a sample user re-call text display file
-
-
-
- Overview: The remainder of this document is structured as follows:
-
- 1. Installation Options - briefly explains where the PPE
- can be installed.
- 2. Installation Usage - describes how to install the PPE
- in simple terms.
- 3. CFG File Function - describes the configuration file.
- 4. PPE Execution - describes how the PPE runs and
- functions.
- 5. CALLER log entries - describes the various entries the
- PPE will make to the PCB CALLER log.
- 6. Support Files - briefly describes the various text
- display and associated support
- files.
- 7. Registration - NONE!! FREE!!
- 8. Updates - describes How/where to obtain
- updates.
- 9. Source code - describes how to obtain the source
- code.
- 10. Distribution - talks about it.
- 11. Disclaimer - attorney said I had to have it.
- 12. Development History - talks about it.
- 13. Other PPEs - other PPEs I have available.
-
-
- Installation
- Options: You have several choices for installation of the PPE.
- Several options are suggested below:
-
- Option 1: Install the PPE in PCBTEXT record #259 (What is
- your first name).
-
- Option 2: Install the PPE in PCBTEXT record #385
- (Operational Languages Available:). To use
- this prompt, you must have the Operational
- Languages feature of PCBoard enabled. To enable
- this function, run PCBSETUP, at Main Menu, select
- Configuration Options, System Control, Multi-
- Language Operation: Y.
-
- Option 3: Install the PPE in PCBTEXT record #149 (Do you
- want graphics (Enter) = no).
-
- Option 4: Imbed the PPE call as the last line in a text
- file, such as the WELCOME files.
-
-
-
- Installation
- Usage: A. Determine the directory in which you desire to place
- the PPE and its support files. They may be placed in
- any directory as long as all the files go there. I
- suggest making a directory \PCB\PPE\CALLBLOC and
- then just unzip CALLBLOC.ZIP in the CALLBLOC directory,
- but again, any directory will work.
-
- B. Next, determine which installation option location
- you desire. The PPE itself can be placed in any of
- these locations:
-
- Options 1,
- 2 or 3: If you desire to install the PPE
- in one of the PCBTEXT file prompt
- locations (i.e. #259, #385, #149)
- then follow the simple procedure
- below:
-
- Step 1: Go to your \PCB directory and
- run program MKPCBTXT.EXE, at the
- file request prompt answer with
- the path/name to your PCBTEXT
- file (probably just enter
- PCBTEXT).
-
- Step 2: MKPCBTXT display screen should
- now appear, Depress F3 key.
-
- Step 3: Answer the prompt with the
- record number you desire, such
- as 259 or 385, etc.
-
- Step 4: The text prompt display will
- now appear (such as: 'What is
- your first name' for #259).
- NOW, edit the field with the
- path/name of the PPE, such as:
- !C:\PCB\PPE\CALLBLOC\CALLBLOC.PPE.
- Don't forget the ! character, it
- is mandatory to cause PCBoard to
- recognize and execute a PPE.
-
- Step 5: Now just save and exit MKPCBTXT.
-
- Step 6: Next and Last, go to the direc-
- tory containing the CALLBLOC files
- and edit the configuration file
- (CALLBLOC.CFG) to your desire,
- see the CFG file description
- below for info. Also, you may
- edit the other text display files
- as you desire.
-
- Option 4: Simply use your text editor to edit the
- desired text file, such as the WELCOME
- files, by adding a new blank 'last' line.
- On this line, enter the PPE call, such
- as: !C:\PCB\PPE\CALLBLOC\CALLBLOC.PPE.
-
-
- C. If your PCBoard modem initialization string does not
- already have CallerID function turned-on, then that
- must be done also.
-
- The PPE obtains the Caller-ID info directly from PCBoard
- software, not the modem itself, so, PCBoard software must
- be set to answer on the 2nd ring and the modem CallerID
- enable command must be placed in the PCBoard modem
- Initialization string or similar setup. (i.e. if PCBoard
- is writing the CallerID info in your CALLER log, then
- the setup is OK, if it isn't, then you must get PCBoard
- and CallerID working first).
-
- NOTES: a. for Supra modems, add the #CID=1 command to
- the modem init string. Also, some sysops
- have reported having to set S110=3 to get
- 14400baud connections. (To perform this, run
- PCBSETUP, at Main Menu, select Modem Informa-
- tion, Modem Setup, Modem Initialization String).
-
- b. To set answer on 2nd ring, run PCBSETUP, at
- Main Menu, select Modem Information, Config-
- uration Switches, Number of Rings Required: 2.
-
- c. To enable PCBoard writing of CID info to
- CALLER log, run PCBSETUP, at Main Menu, select
- Configuration Options, Logging Options, Log
- Connect String to Disk: Y.
-
-
-
- CFG File Function: The CALLBLOC.CFG file provides the Sysop with the
- capability to customize and select options for
- CALLBLOC.PPE to perform. Below is a sample of
- the configuration file and the entry descriptions:
-
- CFG file Built-in Defaults
- ---------------------------- -------------------------------
-
- Line 1 1 1
- Line 2 1 0
- Line 3 1 0
- Line 4 1 1
- Line 5 1 1
- Line 6 @X0EWhat is your FIRST name @X0EWhat is your FIRST name
- Line 7 SYSOP SYSOP
- Line 8 0 0
- Line 9 10 10
-
- ---------------------------- -------------------------------
-
- Line 1: Flag to indicate to do CALLBLOC all caller logging (1=yes,0=no)
-
- Line 2: Flag to indicate write CID info to PCB CALLER log (1=yes, 0=no)
- (NOTE: PCBoard has its own switch to perform this same function,
- accessed via PCBSETUP, Configuration Options, Logging Options,
- Log Connect String to Disk: Y).
-
- Line 3: Flag to indicate to hangup on Private calls (1=yes, 0=no)
-
- Line 4: Flag to indicate force user to re-call if CID info is garbled,
- forces hangup. (1=yes, 0=no)
-
- Line 5: String indicating modem type (1, 2 or prefix string) 1=Supra or
- Practical Peripherals modem, 2=ZyXEL modem, or the phone
- number actual prefix string for other modem types.
-
- For example, Supra CID string is as follows:
-
- CID: DATE = 0108 TIME = 0630 NMBR = 7034509456
-
- Therefore, the Supra modem prefix is "NMBR = ". However,
- the PPE knows this if you just enter a "1". But this
- example is provided for those that have a different CID
- string. The CID string can be seen in the PCB CALLER log.
-
- Line 6: Sysop defined installation option User Prompt (If installing
- in a text file that requires no user prompt then just leave
- this line blank). (If installing in a PCBTEXT prompt, then
- this is the replacement prompt).
-
- Line 7: Addressee (Sysop or Co-Sysop) for Private and Bad call alert
- messages.
-
- Line 8: Flag to indicate if some nodes have non-CID modems. (1=yes,
- 0=no). This lets CALLBLOC know to terminate and assume a non-
- CID capable modem if no CID info is available.
-
- Line 9: The number of digits in your local CallerID service, usually
- 10, but someplaces 7 digits.
-
-
-
- If you desire a faster execution (no disk read access slowdown),
- you can activate the built-in defaults simply by either deleting
- the CALLBLOC.CFG file or renaming it to something else, i.e.
- READ.CFG.
-
-
- NOTE: You must review and edit the CFG file for
- your system and desires.
-
-
-
- PPE Execution: 1. The CALLBLOC.PPE starts execution by displaying
- the text display message "... Searching Phone
- Records ...". However, if the BADCALL.NUM file is
- missing, instead of the previous message, a message
- "...TELL SYSOP BADCALL.NUM file is missing!" is
- displayed and the PPE terminates, returning to normal
- PCBoard user login function.
-
- 2. Next, the PPE performs a simple self-check of BADCALL.NUM
- file to make certain it is a valid file. If the check
- passes, the text message "..CallerID file integrity
- passed..." is displayed on the local BBS display only.
- The check is fairly simple, the first record (entry)
- in the file must be '1234567890'. So, you must always
- leave the first line that way. This is just an extra
- measure to make sure there are no accidental lock-outs
- due to a corrupted file.
-
- If the check fails, a text message "CallerID file
- integrity FAILED!" is displayed on the local BBS screen,
- an alarm is sounded at the BBS PC speaker, and the PPE
- terminates and returns to the normal user login.
-
- 3. When the PPE detects a match, an entry is made in the log
- file. The file contains the date, time, offending phone
- number and a remark.
-
- Next, the bad user is displayed the BADCALL display file,
- unless it is missing, and then the message "Tell SysOp
- file BADCALL is missing!" is displayed on BBS screen.
- Either way, the next step is an immediate HANGUP on
- the user.
-
- 4. When the PPE completes, the message "CALLBLOC Successfully
- Completed!" is displayed on the local screen only.
-
-
-
- CALLER log entries: Listed below are examples of entries that CALLBLOC
- can make to the PCB CALLER log:
-
- 1. 'No CALLERID info available! (CALLBLOC.PPE)' -
- indicates CID data was not read for some
- reason, perhaps a poor phone line connection
- or CID command not active for modem or a
- non-CID capable modem.
-
- 2. 'CALLBLOC.PPE using built-in defaults' - the
- CALLBLOC.CFG file does not exist so PPE has
- switched to built-in defaults.
-
- 3. 'CID Number not = 10 digits (CALLBLOC.PPE)' -
- CID info read was not complete, probably due to
- noisy phone line.
-
- 4. 'Verify proper CID Key for your modem!
- (CALLBLOC.PPE)' - CID prefix key selected is
- not correct or very bad phone line.
-
- 5. 'Garbage found in CID number! (CALLBLOC.PPE)' -
- CID read info was corrupted--probable poor
- phone line.
-
- 6. 'File BLOCKED is missing! (CALLBLOC.PPE)'
-
- 7. 'Can't find file BADCALL.NUM! (CALLBLOC.PPE)'
-
- 8. 'CallerID file integrity FAILED! (CALLBLOC.PPE)' -
- The first line entry in file BADCALL.NUM is bad.
-
- 9. 'File RECALL is now missing! (CALLBLOC.PPE)'
-
- 10. 'The file BADCALL is missing! (CALLBLOC.PPE)'
-
- 11. 'BADBOY called again! Check Logs..(CALLBLOC.PPE) -
- indicates a match was found.
-
- 12. 'Number in BADCALL.NUM is not 10 digits!' -
- indicates an erroneous number entry in file
- BADCALL.NUM.
-
-
- Support Files:
-
- 1. You must create two files (samples already made in the zip).
- One file named 'BADCALL.NUM' which contains the known bad
- phone numbers to block, one number per line, followed by a
- remark line. The number line format is '2024307269' (only
- the actual number!--or, whatever the format of your caller-id
- service number string). See the example file, it is fairly
- simple. The first entry in the file is an integrity check,
- as described in PPE Execution, paragraph #2 above, so do not
- edit this line. Make sure there are NO blank lines, includ-
- ing a last line, in the file.
-
- The second file is called 'BADCALL' (again, an example
- file is provided). This file is the text display file to be
- shown to the offender just prior to hang-up. Obviously, it
- can be edited to your preference. PCB text file extensions
- for Language, Security and Graphics are recognized.
-
- 2. RECALL is the text display file to be shown to users when
- the CID read info is faulty and the caller is requested
- to call again. Edit it as desired. PCB text file extensions
- for Language, Security and Graphics are recognized.
-
- 3. BLOCKED is the text display file to be shown to users when
- the PPE has detected that the user has Call-Blocking. This
- is also referred to as a Private or Blocked call. Edit it
- as desired. PCB text file extensions for Language, Security
- and Graphics are recognized. If you do not want to display
- this file to the user--then just delete the file and the
- user will receive no display or notice.
-
- 4. BAD-MSG is the text incorporated into the message to the
- Sysop when a bad caller match is detected. Edit it as
- desired.
-
- 5. PRIV-MSG is the text incorporated into the message to the
- Sysop when a Private caller match is detected. Edit it as
- desired.
-
- 6. CALLBLOC.LOG is a sample log file showing one example entry
- for all 3 types of calls.
-
-
-
- Registration: NONE!! As from the beginning (ver. 1.0 of CALLBLOC) there
- is no registration fee. Basic use of the PPE is FREE!!!
-
- However, if you feel compelled that my work is worth
- compensation, I will accept all offers. Thank You!
-
- Also, if you would like to provide suggestions for
- improvement to the PPE, bug reports, or just a note
- of thanks or hello, please forward those as well. See
- below for my mailing address and BBS number. Additionally,
- I frequently browse the RIME Sysop and PCBoard conferences,
- although contacting me there is not as reliable because
- sometimes I get too busy to call.
-
-
- Updates: The latest version of the PPE program can be obtained from
- my BBS: SBG Online! BBS (703) 450-9456. If you have any
- comments or suggestions for improvement, you can leave them
- there also. The file will be found in directory #1 as a
- FREE/NOTIME file. The BBS runs PCBoard 15 at 14400v42bis.
-
-
- Source If you desire a diskette containing the PPL source code so
- Code: you can modify it for your own use, the cost is $15 US. I
- accept cash, money order, VISA or Mastercard. You can place
- an order online on the BBS (703) 450-9456 or by mail at:
- A. Segura, P.O. Box 1089, Sterling, VA, 20167-1089.
-
- EXTRA, EXTRA!! In addition to the CALLBLOC source, you
- will also receive source to a "Last TEN Caller" and
- "Running Log Caller" bulletin generators that I have
- developed as well.
-
- As another option, for $25, you can subscribe to the PPE
- conference on my BBS. The conference will always contain
- the latest version of the source code for CALLBLOC,
- CALLERID, VULGARID and several other PPEs for immediate
- downloading. The subscription period lasts one year. We
- also have the latest version of the PIER Shareware CDROM
- always online. You can even subscribe online with your
- VISA/MC via (S)cript Questionaire #2 for immediate access.
-
-
- Distribution: You may freely distribute this complete package only in an
- unmodified form. No remuneration may be collected or charged
- for this work by anyone other than the below noticed
- individual/company except for that cost incurred in actual
- electronic media production (i.e. diskette or CDROM). In
- other words, it can be placed on BBSs, shareware CDROMS, etc.
- but I/my company reserves the right of copyright and
- remuneration for the actual work. The source code MAY NOT
- be distributed by anyone other than the below listed company.
-
-
- Disclaimer: The user agrees when utilizing this package that he does so
- at his own risk with no guarantees, implied or otherwise, as
- to the functional performance or liability of the package.
-
-
- Development
- History: ver. date remarks
- ---- -------- ---------------------------------------
- 1.0 12/06/93 Initial release.
- 1.1 12/10/93 Added bad caller message to Sysop.
- 1.1JK 03/26/94 Added all caller logging routine at
- request of user John K.
- 2.0 04/06/94 Improved caller logging, added many new
- features including: built-in defaults,
- any directory usage, Blocked call hangup
- and messages, improved modem handling
- routines, user re-call, etc.
- 2.1 04/12/94 added switch for multiple node system
- with mixed (non-CID) modems.
- 2.2 04/15/94 clarified DOC and source statements,
- optimized some code
- 2.3 04/23/94 Fixed bug when in local user mode text
- prompt did not display; deleted ZyXEL.PPE
- 2.4 04/29/94 Added number of CallerID digits switch
- for Gary S. of Lasalle, Quebec.
- 2.5 05/08/94 Improved error-checking slightly to support
- DUP-BLOC.PPE use.
- 2.6 05/21/94 Added Deluxe CID Caller Name Log entries
- (at request of user David E.)
-
-
- ***************************************************************************
- * (c) Copyright 1993 A. Segura/Fax~An~Ad Marketing, Inc. *
- ***************************************************************************
-
-
- Other PPEs:
-
- ********************************************************************
- * Look for these other fine utilities at a BBS near you *
- ********************************************************************
-
- AUTOSUBS.PPE run as a script questionnaire, allows online credit
- card subscriptions to BBS (VISA/MC), completes log
- entries and sends alert message to SysOp. (for
- PCBoard 15)
-
- BULLCHK.PPE performs automated tracking of bulletins read by the
- user and performs a user upgrade when all sysop selected
- bulletins have been read.
-
- CALLERID.PPE performs basic callerid identification, logs info
- in file log and user records if desired, and will
- also display desired text screens to users--must
- have callerid capable modem. Several SysOp config-
- uable options. (for PCBoard 15)
-
- CALLBLOC.PPE performs a call blocking function before the
- user can log on based upon a SysOp defined listing
- of undesirable phone numbers--must have callerid
- capable modem. Even sends the SysOp an alert message.
- (for PCBoard 15)
-
- MAKEBLTN.EXE Top callers, cities, down/uploaders bulletin generator
-
- PADLOADS.EXE Automated uploads directory padder--makes your BBS look
- more active with more daily uploads.
-
- REPORT.EXE Program generates reports of CallerID info, user record
- phone numbers, common passwords and several other goodies
- to aid Sysop in identifying abusive or questionable users.
-
- VULGAR.PPE performs a vulgar word/phrase check on user names and
- city entries based on a file of names defined by
- SysOp, and performed before complete newuser login.
- (for PCBoard 15)
-
- VULGARID.PPE same program as VULGAR.PPE except it automatically
- passes the callerid info to CALLBLOC.PPE program
- for future lock-outs. (must have both programs and a
- modem that supports callerid) (for PCBoard 15)
-
- NOTE: VULGARID ver. 1.x only works with CALLBLOC
- ver. 1.x. VULGARID ver. 2.x only works
- with CALLBLOC ver. 2.x.
-
- ***************************************************************************
- * (c) Copyright 1993 A. Segura/Fax~An~Ad Marketing, Inc. *
- ***************************************************************************